System and method for search operations

ABSTRACT

Systems and methods, applicable, for example, in employing a user&#39;s social network in providing that user with results to searches for individuals, businesses, content (e.g., pictures, music, software, and/or the like), and/or the like. Further, systems and methods whereby, for example, information regarding individuals having social connection to individuals, businesses, and/or the like identified via such search may be available.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 10/870,205, filed Jun. 17, 2004, the content of which isincorporated herein by reference in its entirety.

FIELD OF INVENTION

This invention relates to systems and methods for search operations.

BACKGROUND INFORMATION

In recent years, there has been an increase in the use of computers forsearch. For example, many people have come to employ Internet searchengines, online directories, and the like in preference to conventionalresources such as public libraries, paper telephone directories, and thelike.

Accordingly, there may be interest in technologies that facilitate suchuse of computers.

SUMMARY OF THE INVENTION

According to various embodiments of the present invention there areprovided systems and methods applicable, for example, in employing auser's social network in providing that user with results to searchesfor individuals, businesses, content (e.g., pictures, music, software,and/or the like), and/or the like.

It is noted that, according to various embodiments, informationregarding, for instance, individuals having social connection toindividuals, businesses, and/or the like identified via such search maybe available. In various embodiments, information regarding the fitness,quality, and/or the like of a found result (e.g., an individual orbusiness) might be provided (e.g., from the viewpoint of search criteriaand/or the like).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows exemplary steps involved in search functionality accordingto various embodiments of the present invention.

FIG. 2 shows exemplary steps involved in identity functionalityaccording to various embodiments of the present invention.

FIG. 3 shows exemplary steps involved in evaluation functionalityaccording to various embodiments of the present invention.

FIG. 4 shows an exemplary computer.

FIG. 5 shows a further exemplary computer.

DETAILED DESCRIPTION OF THE INVENTION General Operation

According to embodiments of the present invention there are providedsystems and methods applicable, for example, in employing a user'ssocial network in providing that user with results to searches forindividuals, businesses, content (e.g., pictures, music, software,and/or the like), and/or the like. Such searches might, for instance,seek individuals, businesses, and/or the like that match specifiedcriteria.

In various embodiments, information regarding, for instance, individualshaving social connection to individuals, businesses, and/or the likeidentified via such search may be available. Moreover, in variousembodiments, evaluations, rankings, and/or the like regardingindividuals, businesses, and/or the like identified via such search maybe available.

In various embodiments, various functionality regarding security,privacy, and/or the like may be implemented.

Various aspects of the present invention will now be discussed ingreater detail.

Search Functionality

According to various embodiments of the present invention, a user of anode and/or other computer wishing that his social network be employedin searching for individuals, businesses, and/or the like might, forexample, indicate such a desire through a graphical user interface (GUI)and/or other interface provided by his node and/or other computer.

With respect to FIG. 1 it is noted that the user could, in variousembodiments, provide, perhaps via the GUI and/or other interface,various criteria regarding the search to be performed (step 101). Forexample, the user might be able to specify the type of results that hewished to receive (e.g., individuals, businesses, and/or content).

As another example, the user might be able to specify variouscharacteristics, attributes, words, phrases, and/or the like as criteriafor the search. The characteristics, attributes, and/or the like might,in various embodiments, correspond to data held in profiles. Data heldby profiles might include, for example, data regarding names, genders,ages, marital statuses, birthdays, email addresses, mobile telephonenumbers, landline telephone numbers, fax numbers, universal resourcelocators (URLs), street addresses, cities, countries, jobs, companies,industries, professional experiences, educational information (e.g.,degrees, graduation years, and/or schools), interests, stored publiccontent, schedule information (e.g., diary), shared logs (e.g., visitedplaces), and/or the like. It is noted that, in various embodiments,certain data held by a profile might be searchable by keyword. It isfurther noted that, in various embodiments, search criteria might beprovided in Boolean form and/or the like.

Moreover, in various embodiments, search criteria might be able toinclude specifications of ranges of values (e.g., that a criteria have avalue falling between two specified values), indication of “null”,specification that search consider criteria similar to specified data bematching (e.g., words and/or phrases that sound like a specified wordand/or value, that are synonyms, similar to, and/or the like withrespect to a specified word and/or value, and/or the like), and/or thelike. Accordingly, in various embodiments, “between”, “like”, and/or thelike might be specifiable in searches.

In various embodiments, a depth indicator could be associated with asearch. Such a depth indicator could, for instance, serve to specifyextent of propagation of a search among nodes and/or other computers.The depth indicator associated with a search could be established in anumber of ways. For instance, in various embodiments the depth indicatormight be settable by the user (e.g., via a GUI and/or other interfaceprovided by the node and/or other computer), a system administrator, aservice provider, a manufacturer of the node and/or other computer,and/or the like. It is noted that, in various embodiments, depthindicators could be set for one or more specific searches, for allsearches, for all searches matching certain criteria, and/or the like.It is noted that, in various embodiments, a depth indicator could, forexample, act to define limits for a search within a social network. Itis further noted that, in various embodiments, in the case where a depthindicator was depleted, had reached a certain threshold, and/or thelike, propagation might proceed no further. Such a threshold might, invarious embodiments, be set by a system administrator, service provider,and/or the like.

The user's node and/or other computer could, in various embodiments, actto dispatch one or more search messages corresponding to a search to beperformed on behalf of its user (step 103). For instance, the nodeand/or other computer could act to dispatch one or more search messagesto some or all nodes and/or other computers referenced in its stored oneor more contacts, address book, logs (e.g., regarding sent and/orreceived calls, emails, Short Message Service (SMS) messages, MultimediaMessaging Service (MMS) messages, Bluetooth messages, and/or the like,mobile life blogs (e.g., logs regarding visited places, people met,and/or the like)), and/or the like.

It is noted that, in various embodiments, the user could, perhaps via aGUI and/or other interface, be able to specify that such search messagesbe sent to all nodes and/or other computers referenced in the storedcontacts, address book, logs, and/or the like, to only certain suchnodes and/or other computers (e.g., specified nodes and/or othercomputers, nodes and/or other computers matching specified criteria,nodes and/or other computers marked “public” and/or the like, nodesand/or other computers marked “private” and/or the like, nodes and/orother computers members of one or more certain contact groups and/or thelike, and/or the like), and/or the like. It is noted that, in variousembodiments, an appropriate depth indicator could be included in suchone or more search messages and/or dispatched therewith.

Search messages could be dispatched in a number of ways. For example,SMS, MMS, Unstructured Supplementary Service Data (USSD), Simple ObjectAccess Protocol (SOAP), Remote Method Invocation (RMI), Java MessagingService (JMS), object push, Session Initiation Protocol (SIP),Transmission Control Protocol (TCP), General Packet Radio Service(GPRS), Universal Mobile Telecommunications Service (UMTS), Bluetooth,Ultra Wideband (UWB), wireless Firewire, Infrared Data Access (IrDA),WiFi (e.g., 802.11a, 802.11b, and/or 802.11g), wired connections (e.g.,Ethernet), secure shell (SSH), and/or the like might be employed.

In various embodiments, authentication might be performed. It is furthernoted that, in various embodiments, a network operation and/or the likecould, perhaps temporarily, bind a networking address (e.g., an InternetProtocol (IP) address or Bluetooth address) for a node and/or othercomputer to a host name incorporating a phone number and/or the likecorresponding to the node and/or other computer. To illustrate by way ofexample, where a node and/or other computer had a phone number“212-555-1212”, and a network operator was associated with a particulardomain (e.g., samplenetworkoperator.com), a network address for the nodeand/or other computer might be bound to the host name2125551212.samplenetworkoperator.com,2125551212.nodes.samplenetworkoperator.com, and/or the like.

It is further noted that, in various embodiments, a node and/or othercomputer might advertise alternative network addresses to other nodesand/or other computers. Such, an alternative address might, forinstance, be used for subsequent queries, messages, and/or the likeinstead of the original one. To illustrate by way of example, where anode and/or other computer is reachable via a phone number“212-555-1212” and an IP address 10.30.1.17, another node and/orcomputer might, for instance, use the IP address for subsequent queriesinstead of, for instance, SMS over GSM. Additionally, a node and/orother computer might, for example, store various network addresses forcontacts and change these subsequently, for instance, as the contactschanged their network addresses (e.g., in the case of dynamicallychanging IP addresses in a GPRS system). Alternately or additionally,SMS, MMS, and/or the like might, in various embodiments, be employed forvarious communications in the case where a network address was notknown, not available any more (e.g., in the case where a node and/orother computer reached a region where there was GSM coverage but notGPRS coverage), and/or the like.

Included in search messages could, in various embodiments, be datacorresponding to the search (e.g., specification of type of results,specification of various characteristics, attributes, and/or the like,and/or the like), a depth indicator, an identifier and/or the likeemployable in reaching the user's node and/or other computer (e.g., atelephone number, networking address (e.g., IP address), and/or thelike), and/or the like. It is noted that, in various embodiments, someor all of such data might be in encrypted form, hashed form (e.g.,message digest 5 (MD5) form), and/or the like. It is noted that, invarious embodiments, a search message might contain one or more publickeys.

It is noted that, in various embodiments, included with one or more suchmessages could be one or more profiles (e.g., a profile corresponding tothe user, a business with which the user was affiliated, and/or thelike). Profiles might be so included in accordance with a specificationprovided via the user, via defaults set by the user, and/or he like.Such specification, defaults, and/or the like might be provided, forinstance, via a GUI and/or other interface.

A node and/or other computer receiving one or more search messages (step105) might, in various embodiments, act to determine if it held anyprofiles that matched specified search criteria (step 107). In the casewhere such a matching profile was found, the node and/or other computerreceiving one or more search messages could, in various embodiments, actto provide some or all of that profile to the user's node and/or othercomputer (step 109). In various embodiments, the node and/or othercomputer receiving one or more search messages might act to only providethose portions of a profile that had been specified to be “public”. Suchspecification might, for example, be made by an individual, business,and/or the like associated with the profile, perhaps via a GUI and/orother interface provided by a node and/or other computer of theindividual, business, and/or the like.

It is noted that, in various embodiments, a node and/or other computermight not possess profiles associated with other nodes and/or othercomputers (e.g., corresponding to users of other nodes and/or othercomputers, to businesses affiliated with users of other nodes and/orother computers, and/or the like), and instead might only possessprofiles with which it was associated (e.g., the node and/or othercomputer might only possess one or more profiles corresponding to itsown user, to one or more businesses affiliated with its own user, and/orthe like). Accordingly, the node and/or other computer might, in variousembodiments, act in response to one or more search messages, asappropriate, to provide some or all of one or more matching heldprofiles with which it was associated, to forward one or more of thereceived search messages to some or all nodes and/or other computersreferenced in its stored contacts, address books, logs, and/or the like,and/or the like.

It is further noted that, in various embodiments, each node and/or othercomputer receiving the one or more search messages might, perhaps in amanner analogous to that discussed above, act to forward the one or morereceived search messages to some or all nodes and/or other computersreferenced in its stored contacts, address books, logs, and/or the like(step 111). In the case where a depth indicator had been included in thereceived one or more search messages, the nodes and/or other computersthat had received the one or more search messages from the user's nodeand/or other computer might, in various embodiments, consult the depthindicator before performing such forwarding, and only act to perform theforwarding in the case where, for example, the depth indicator had notbeen depleted (e.g., had not reached zero), the depth indicator had notreached a certain threshold, and/or the like.

Moreover, in various embodiments the nodes and/or other computers thatreceived the one or more search messages from the user's node and/orother computer could, in various embodiments, act to alter such a depthindicator before forwarding it to the some or all nodes and/or othercomputers referenced in stored contacts, address books, logs, and/or thelike. For instance, the depth indicator could be decremented by one.

The nodes and/or other computers that receive the forwarded one or moresearch messages could, in various embodiments, act in a manner analogousto the nodes and/or other computers that received the one or more searchmessages from the originating node and/or other computer. Accordingly,for instance, each such node and/or other computer could act, perhaps ina manner analogous to that discussed above, to determine if it held aprofile that matched specified search criteria, act to provide some orall of such matching profiles to the originating node and/or othercomputer, act to forward the one or more search messages that it hadreceived to some or all nodes and/or other computers referenced instored contacts, address books, logs, and/or the like, act to consultand or alter a corresponding depth indicator, and/or the like.

Accordingly, the one or more search messages dispatched by theoriginating node and/or other computer could, in various embodiments,come to be received by a number of nodes and/or other computers inaccordance with a social network of the originating node and/or othercomputer's user characterized, for instance, by connections betweennodes and/or other computers established by entries in held contacts,address books, logs, and/or the like, and/or by depth indicatorsettings.

It is noted that, in various embodiments, in the case where a nodeand/or other computer, that possessed one or more profiles matchingspecified search criteria associated with one or more search messages,had received those search messages via forwarding performed by more thanone node and/or other computer (e.g., where the same one or more searchmessages had been forwarded to the node and/or other computer by threedifferent nodes and/or other computers), the node and/or other computercould, in various embodiments, act to inform the originating node and/orother computer of this fact. Such functionality could be implemented ina number of ways.

For example, in providing some or all matching profiles to theoriginating node and/or other computer, indication of the number ofnodes and/or other computers that had so forwarded the one or moresearch messages might also be provided. Such a value could, in variousembodiments, be interpreted as an indication of the number ofindividuals having social connection to individuals, businesses, and/orthe like corresponding to the profiles.

As another example, the matching profiles and/or portions thereof couldbe provided to the node and/or other computer that initiated the searchmultiple times, one time for each node and/or other computer that had soforwarded the one or more search messages.

According to various embodiments of the present invention, theoriginating node and/or other computer might act to inform its user ofresults of the search. For instance, the user might, perhaps via a GUIand/or other interface of his node and/or other computer, be presentedwith some or all of received matching profiles and/or portions thereof.It is noted that, in various embodiments, a user could specify a searchusing Structured Query Language (SQL) format and/or the like, dispatchedsearch messages could include search strings in SQL format and/or thelike, and/or the like.

It is noted that, in various embodiments, information regarding thefitness, quality, and/or the like of a found result (e.g., an individualor business) might be provided (e.g., from the viewpoint of searchcriteria and/or the like).

Identity Functionality

According to various embodiments of the present invention, the nodeand/or other computer from which the one or more search messagesoriginated may take action to obtain information regarding individualshaving social connection to individuals, businesses, and/or the likeidentified as satisfying the search. With respect to FIG. 2 it is notedthat, in various embodiments, such information might, in variousembodiments, be provided in response to a request by the node and/orother computer's user (step 201). For example, the user might requestthat such information be provided for one or more indicated individuals,businesses, and/or the like identified as satisfying a search request.The user might provide such a request, for instance, via a GUI and/orother interface provided by the originating node and/or other computer.

In taking such action the originating node and/or other computer might,in various embodiments, act to dispatch one or more identity requestmessages to some or all nodes and/or other computers referenced in itsstored contacts, address books, logs, and/or the like (step 203).

Included in such one or more identity request messages may, in variousembodiments, some or all of the one or more search messages that yieldedthe indicated individuals, businesses, and/or the like (e.g.,specification of type of results, specification of variouscharacteristics, attributes, and/or the like, and/or the like), variousdata corresponding to the indicated individuals, businesses, and/or thelike (e.g., some or all of one or more corresponding profiles receivedby the originating node and/or other computer responsive to the one ormore search messages such as, for instance, one or more phone numbers),a depth indicator, an identifier and/or the like employable in reachingthe originating node and/or other computer (e.g., a telephone number,networking address (e.g., IP address), and/or the like), and/or thelike.

A node and/or other computer receiving such one or more identity requestmessages (step 205) might, in various embodiments, act to determine ifits stored contacts, address books, logs, and/or the like referenced oneor more individuals, businesses, and/or the like corresponding to theone or more identity request messages (step 207). Such functionalitycould be implemented in a number of ways. For instance, a node and/orother computer receiving the one or more identity request messages mightact to determine if its stored contacts, address books, logs, and/or thelike held data (e.g., a phone number) matching profile information(e.g., a phone number) received via the one or more identity requestmessages.

In the case where a node and/or other computer receiving the one or moreidentity request messages determined that its stored contacts, addressbooks, logs, and/or the like referenced one or more individuals,businesses, and/or the like corresponding to the one or more identityrequest messages, the node and/or other computer, perhaps afterreceiving permission to do so from its user, may act to dispatchinformation regarding the identity of its user to the originating nodeand/or other computer (step 209). Such permission might, for example, bereceived via a provided GUI and/or other interface. It is noted that, invarious embodiments, in the case where a user gave no answer to a queryfor such permission, operation could proceed as if the user had answeredthe request for permission in the negative. It is further noted that, invarious embodiments, the user might be able to choose not to receivenotification about incoming search messages (e.g., via a provided GUIand/or other interface), and where the user makes such a choice the nodeand/or other computer might, for instance, dispatch informationregarding the identity of the user automatically, without userintervention, and/or the like.

Among such dispatched information regarding the user could, in variousembodiments, be some or all of the profile of the user, some or all ofan entry corresponding to the user in stored contacts, an address book,a log, and/or the like, and/or the like. Accordingly, for instance, aname and/or phone number for the user might be dispatched.

In various embodiments, the nodes and/or other computers receiving theone or more identity request messages from the originating node and/orother computer might, perhaps in a manner analogous to that discussedabove, act to forward the one or more received identity request messagesto some or all nodes and/or other computers referenced in held contacts,address books, logs, and/or the like (step 211). In various embodiments,in the case where a depth indicator had been included in the receivedone or more identity request messages, the nodes and/or other computersthat had received the one or more identity request messages from theoriginating node and/or other computer might act in a manner analogousto that discussed above with regard to the depth indicator.

The nodes and/or other computers that received the forwarded one or moreidentity request messages could, in various embodiments, act in a manneranalogous to the nodes and/or other computers that received the one ormore identity request messages from the originating node and/or othercomputer.

Evaluation Functionality

It is noted that, in various embodiments, evaluations, rankings, and/orthe like might be provided for one or more indicated individuals,businesses, and/or the like identified as satisfying a search request.Such functionality could be implemented in a number of ways.

With respect to FIG. 3 it is noted that, for instance, in the case wherea node and/or other computer receiving one or more identity requestmessages determined that its stored contacts, address books, logs,and/or the like referenced one or more individuals, businesses, and/orthe like corresponding to the one or more identity request messages(step 301), the node and/or other computer might act to dispatch to thenode and/or other computer from which the one or more identity requestmessages originated one or more evaluations, rankings, and/or the likecorresponding to those individuals, businesses, and/or the like (step307).

Accordingly, for example, such a node and/or other computer thatreceived one or more identity request messages might, perhaps via a GUIand/or other interface, query its user as to whether or not he wished toprovide an evaluation, ranking, and/or the like for one or more of thereferenced one or more individuals, businesses, and/or the like (step303). In the case where the user responded in the affirmative the nodeand/or other computer could, in various embodiments, query its user forevaluation, ranking, and/or the like (step 305). Such querying might,for instance, be done via a GUI and/or other interface.

It is noted that, in various embodiments, the node and/or other computercould store one or more evaluations, rankings, and/or the likepreviously provided by its user and, in various embodiments, could,perhaps after seeking permission from its user (e.g., via a GUI- and/orother interface) dispatch one or more such previous evaluations,rankings, and/or the like instead of and/or in addition to querying itsuser for a new evaluation, ranking, and/or the like just discussed.

It is further noted that, in various embodiments, previous evaluations,rankings, and/or the like might be stored with respect to the evaluated,ranked, and/or the like individuals, businesses, and/or the like. Thenode and/or other computer might, for instance, maintain a cache ofevaluations, rankings, and/or the like, for example, in the form of afirst-in-first-out (FIFO) buffer and/or the like.

Alternately or additionally, in various embodiments, previousevaluations, rankings, and/or the like might be stored with respect tothe evaluated, ranked, and/or the like individuals, businesses, and/orthe like along with corresponding queries, messages, and/or the like.For example, a contact might be ranked, evaluated, and/or the like, in adifferent manner if considering him as a professional as opposed to thecase where being considered with respect to his hobbies, interests,and/or the like.

It various embodiments, in querying its user for one or moreevaluations, rankings, and/or the like, the node and/or other computercould, perhaps via a GUI and/or other interface, inform its user of oneor more previous corresponding evaluations, ranks, and/or the like, andquery its user as to whether he wished to provide one or more newevaluations, rankings, and/or the like to the node and/or other computerfrom which the one or more identity request messages originated, or ifhe wished for the node and/or other computer from which the one or moreidentity request messages originated to receive previously providedevaluations, rankings, and/or the like.

It is noted that, in various embodiments, a user could choose to includeone or more profiles along with evaluations, rankings and/or the like(e.g., a profile corresponding to the user, a business with which theuser was affiliated, and/or the like). Profiles might be so included inaccordance with a specification provided by the user, via defaults setby the user, and/or the like. Such specification, defaults, and/or thelike might be provided, for instance, via a GUI and/or other interface.

It is further noted that, in various embodiments, statisticalrepresentations (e.g., averages) that took into account evaluations,rankings, and/or the like may be made available to a node and/or othercomputer (e.g., one from which the one or more identity request messagesoriginated). Such a statistical representation might, perhaps, beweighted (e.g., a weighed average).

In various embodiments, a node and/or other computer could come toreceive various evaluations, rankings, and/or the like specified byvarious individuals with respect to various individuals, businesses,and/or the like. For instance, in various embodiments, evaluations,rankings, corresponding statistical representations, and/or the like maybe propagated among nodes and/or other computers. Such nodes and/orother computers could, in various embodiments, employ such receivedevaluations, rankings, and/or the like in a number of ways. For example,such evaluations, rankings, and/or the like could be employed such thatsearch requests would have a higher probability of yieldinghighly-regarded individuals, businesses, and/or the like than lesshighly-regarded individuals, businesses, and/or the like. Suchfunctionality could be implemented a number of ways.

For example, in the case where such a node and/or other computerpossessed more than one profile that that could satisfy a searchrequest, the node and/or other computer might choose for dispatch to thenode and/or other computer from which the search request originated oneor more such profiles, with the probability of a particular such profilebeing chosen being determined, for instance, by the extent to which itwas highly regarded according to evaluations, rankings, and/or the like.Accordingly, for instance, each such profile being considered asresponsive to the search request might be assigned a value determined bythe extent to which it was highly regarded according to evaluations,rankings, and/or the like. In various embodiments, the sum of all suchassigned values for a set of profiles considered responsive to thesearch request might add up to one.

It is noted that, in various embodiments, a node and/or other computerso possessing more than one profile that could satisfy a search requestmight posses a cache of profiles received from various nodes and/orother computers. Such a cache could be filled in a number of ways.

For example, profiles might be exchanged, transferred, and/or the likebetween nodes and/or other computers, provided to one or more serversand/or the like, and/or the like. In various embodiments, in suchexchange, transfer, and/or the like, certain profile fields (e.g.,non-public fields) might only be sent if the recipient was also sendingprofiles that included those fields, a node and/or other computer mightonly send its user's profile to a recipient if that recipient wasreferenced in held contacts, a held address book, a held log, and/or thelike, if a preference set by its user indicated that that the recipientshould receive specified profiles (e.g., profiles corresponding to theuser, other profiles, and/or the like), and/or the like. In variousembodiments, profile exchange, transfer, and/or the like might, in thecase where a profile to be sent was already held by the recipient, actto update any changed fields rather than to send the entire profile.

Moreover, in various embodiments, profile exchange might happen duringan established connection (e.g., a telephone call between nodes and/orother computers). It is further noted that, in various embodiments,profile exchange, transfer, and/or the like might be performed in amanner analogous to that above (e.g., via object push). As anotherexample, a node and/or other computer might come to possess one or moreprofiles by acting to store profiles that it received for purposes ofpassing it to an intended recipient (e.g., that it received from onenode and/or other computer for purposes of passing to another nodeand/or other computer).

It is noted that, in various embodiments, in the case where a nodeand/or other computer possessed in held contacts, a held address book, aheld log, and/or the like reference to one or more nodes and/or othercomputers expected to hold profiles responsive to a search request, thenode and/or other computer could act, perhaps in a manner analogous tothat discussed above, to forward the corresponding one or ore searchmessages to one or more of such nodes and/or other computers, with theprobability of a particular node and/or other computer receiving theforwarding being determined, for instance, by the extent to which it wasregarded according to evaluations, rankings, and/or the like (e.g.,according to an average, weighted average, and/or other statisticalrepresentation regarding such evaluations, rankings, and/or the like).

The functionality by which the node and/or other computer could expect anode and/or other computer to hold a profile responsive to the searchrequest could be implemented in a number of ways. For instance, the nodeand/or other computer might, perhaps as discussed above, hold a numberof evaluations, rankings, and/or the like for a number of individuals,businesses, and/or the like, and for each such held evaluation, ranking,and/or the like have one or more corresponding values (e.g., phonenumbers) of the sort held by one or more held contacts, address books,logs, and/or the like such that, in forwarding a received search requestto one or more nodes and/or other computers referenced by held contacts,address books, logs, and/or the like, it could recognize such a nodeand/or other computer as one whose corresponding individual, businesses,and/or the like was viewed with a certain regard (e.g., had a certainaverage evaluation, ranking, and/or the like) with respect to thecharacteristics and/or the like specified, sought, and/or the like bythe search request. It is noted that, in various embodiments, a weighedaverage might be employed.

It is noted that, in various embodiments, it might be possible for auser to agree to provide a ranking, evaluation, and/or the like, but torequest that that ranking, evaluation, and/or the like be anonymous.Accordingly, for example, a node and/or other computer receiving theevaluation, rank, and/or the like might not receive specification of theuser that provided the rank, evaluation, and/or the like, the identityof that user might not be made available to the user of the node and/orother computer receiving the rank, evaluation, and/or the like, and/orone or more intermediate nodes and/or other computers might be employedin the dispatch of the ranking, evaluation, and/or the like from thenode and/or other computer dispatching the ranking, evaluation, and/orthe like.

In various embodiments, a user might be queried via a GUI and/or otherinterface provided by his node and/or other computer as to whether ornot he was willing to have his identity revealed with regard to aranking, evaluation, and/or the like. Moreover, in various embodiments,a user might be able to set a preference indicating that his evaluation,rankings, and/or the like be or not be anonymous, be or not be anonymousby default (e.g., that a GUI and/or other interface would query him, buthis default would be considered the default answer by the interface),and/or the like.

It is noted that, in various embodiments, an evaluation, ranking, and/orthe like of a individual, business, and/or the like might be providedresponsive to a search request and/or not responsive to one or moreidentity request messages. It is further noted that, in variousembodiments, a node and/or other computer's user might be able tospecifically request evaluation, ranking, and/or the like. Moreover, invarious embodiments, a node and/or other computer may dispatch one orore evaluation request messages and/or the like.

Centralized Operation

According to various embodiments of the present invention, variousfunctionality discussed above could, perhaps in a manner analogous tothat discussed above, be employed in centralized operation.

In various embodiments of the present invention, a node and/or othercomputer originating a search request may act to dispatch one or moresearch messages to one or more centralized servers and/or the like. Suchone or more search messages might, for instance, be as discussed aboveand/or could, for instance, be dispatched as discussed above (e.g., TCP,SSH, SMS, MMS, and/or the like might be employed). As noted above, someor all data included in the one or more search messages might, variousembodiments, be encrypted, hashed, and/or the like. In variousembodiments, authentication may be performed. It is noted that, invarious embodiments, a user could specify a search using SQL formatand/or the like, dispatched search messages could include search stringsin SQL format and/or the like, and/or the like.

The one or more centralized servers and/or the like could, in variousembodiments, receive one or more contacts, address books, logs,profiles, and/or the like, and/or portions thereof, from nodes and/orother computers. It is noted that, In various embodiments, suchcontacts, address books, logs, profiles, and/or portions thereof may bereceived by the one or more servers and/or the like in encrypted form,hashed form (e.g., MD5 form and/or the like), and/or the like, and/orencryption, hashing, and/or he like might be performed after receipt.

Having received such one or more search messages the one or morecentralized servers and/or the like could, in various embodiments, actto process the one or more search messages in view of contacts, addressbooks, logs, profiles, and/or the like, and/or portions thereof, thathad been received from one or more nodes and/or other computersreferenced by contacts, address books, logs, and/or the like (and/orportions thereof) received from the node and/or other computer that haddispatched the one or more search messages.

It is noted that, in various embodiments, the referencing to the one ormore nodes and/or other computers by the contacts, address books, logs,and/or the like (and/or portions thereof) received from the node and/orother computer that had dispatched the one or more search messages mightbe in the form of hashed values and/or the like (e.g., hashed telephonenumbers), and these hashed values and/or the like might be matched withhashed values associated with the referenced nodes and/or othercomputers.

In performing the processing the one or more servers and/or the likecould, in various embodiments, act to determine if any profiles receivedfrom the referenced one or more nodes and/or other computers matchedspecified search criteria. In the case where such a matching profile wasfound, the one or more servers and/or the like could, in variousembodiments, act to make some or all of that profile available to thenode and/or other computer from which the one or more search messagesoriginated. In various embodiments, perhaps in a manner analogous tothat discussed above, the one or more servers and/or the like might actto only provide those portions of a profile that had been specified tobe “public”.

The one or more servers and/or the like could act to make some or all ofthe profile available to the node and/or other computer from which theone or more search messages originated in a number of ways. For example,dispatch could be performed in a manner analogous to that discussedabove. As another example, the one or more servers and/or the like couldmake some or all of the profile available for later retrieval by thenode and/or other computer.

Accordingly, for instance, the node and/or other computer couldperiodically poll the one or more servers and/or the like to see if datawas available for retrieval, and could, perhaps after receivingpermission from its user (e.g., via a GUI and/or other interface)retrieve data that had been available. Such polling, retrieval, and/orthe like might, for instance, be performed in a manner analogous to thatdiscussed above (e.g., using TCP, SSH, SMS, MMS, and/or the like). It isnoted that, in various embodiments, polling could involve provision ofhashed identifiers, phone numbers, and/or the like.

It is noted that, in various embodiments, the one or more servers and/orthe like might make available to the node and/or other computer fromwhich the one or more search messages originated only one or moreidentifiers corresponding to an individual, business, and/or the likehaving a matching profile. One or more of such identifiers might, invarious embodiments, be encrypted, and/or corresponding hashes (e.g.,MD5 hashes) might be provided.

The one or more servers and/or the like might, in various embodiments,consult contacts, address books, logs, and/or the like, and/or portionsthereof that had been received from the referenced one or more nodesand/or other computers to determine nodes and/or other computersreferenced by those contacts, address books, logs, and/or the like,and/or portions thereof. The one or more servers could, in variousembodiments, act with respect to one or more of the nodes and/or othercomputers referenced by those contacts, address books, logs, and/or thelike, and/or portions thereof, in a manner analogous to that discussedabove with respect to nodes and/or other computers referenced bycontacts, address books, logs, and/or the like, and/or portions thereofthat had been received from the node and/or other computer from whichthe one or more search messages originated.

Accordingly, in various embodiments, processing of contacts, addressbooks, logs, profiles, and/or the like, and/or portions thereof that hadbeen received from various nodes and/or other computers could traversesocial connections among nodes and/or other computers, characterized,for instance, by node and/or other computer references in receivedcontacts, address books, logs, and/or the like, in a manner perhapsanalogous to that discussed above with respect to search messageswherein, for example, search messages are propagated among nodes and/orother computers in accordance with social connections.

According to various embodiments of the present invention, in the casewhere it was desired to, for example, obtain information regardingindividuals having social connection to individuals, businesses, and/orthe like identified as responsive to a search request a node and/orother computer might act to dispatch one or more identity requestmessages to the one or more servers and/or the like.

Such one or more identity request messages could, for example, be of thesort discussed above and/or could be dispatched as discussed above.Alternately or additionally one or more identity request messages could,in various embodiments, convey one or more phone numbers, identifiers,and/or the like, and/or corresponding hashes, corresponding to anindividual, business, and/or the like having a profile matching a searchrequest.

Alternately or additionally, the node and/or other computer might sodispatch one or more identity request messages to the one or moreservers and/or the like in the case where it was desired to receive theidentity, profile, and/or the like for an individual, business, and/orthe like that had a profile identified as responsive to a searchrequest.

In various embodiments, the one or more centralized servers and/or thelike, having received one or more identity request messages seekinginformation regarding individuals having social connection toindividuals, businesses, and/or the like identified as satisfying asearch request, could, for example, act to process the one or moreidentity request messages in view of contacts, address books, logs,and/or the like, and/or portions thereof, that had been received fromone or more nodes and/or other computers referenced by contacts, addressbooks, logs, and/or the like (and/or portions thereof) received from thenode and/or other computer that had dispatched the one or more identityrequest messages.

In performing such processing the one or more servers and/or the likecould, in various embodiments, act to determine if reference was made,by contacts, address books, logs, and/or the like, and/or portionsthereof, that had been received from one or more nodes and/or othercomputers referenced by contacts, address books, logs, and/or the like(and/or portions thereof) received from the node and/or other computerthat had dispatched the one or more identity request messages, to one ormore individuals, businesses, and/or the like corresponding to the oneor more identity request messages. Such functionality could, forexample, be implemented in a manner analogous to that discussed above.It is noted that, in various embodiments, some or all of the identityrequest messages, contacts, address books, logs, and/or the like, and/orportions thereof, might be in encrypted form and/or corresponding hashesmight exist and, in various embodiments, such encrypted forms and/orhashes might be employed in processing.

In the case where it was determined that a node and/or other computerheld contacts, address books, logs, and/or the like referencing one ormore individuals, businesses, and/or the like corresponding to the oneor more received identity request messages, the one or more serversand/or the like could, in various embodiments, act to, perhaps afterseeking permission to do so from one or more individuals, businesses,and/or the like affiliated with that node and/or other computer, makeavailable information regarding the identity of the one or moreindividuals, businesses, and/or the like affiliated with that nodeand/or other computer to the node and/or other computer that dispatchedthe one or more identity request messages.

Such functionality could be implemented in a number of ways. Forexample, permission could, in various embodiments, be sought in a manneranalogous to that discussed above (e.g., via polling, dispatch, GUIand/or other interface, and/or the like). Moreover, in variousembodiments, the information regarding the identity of the one or moreindividuals, businesses, and/or the like could be made available in amanner analogous to that discussed above (e.g., via polling, dispatch,GUI and/or other interface, and/or the like).

As a next step the one or more servers and/or the like could, in variousembodiments, consult contacts, address books, logs, and/or the like,and/or portions thereof that had been received from one or more nodesand/or other computers referenced by contacts, address books, logs,and/or the like (and/or portions thereof) received from the node and/orother computer that had dispatched the one or more identity requestmessages. Via this consultation, the one or more servers and/or the likecould, for instance, act to determine nodes and/or other computersreferenced by those contacts, address books, logs, and/or the like,and/or portions thereof.

The one or more servers could, in various embodiments, act with respectto one or more of the nodes and/or other computers referenced by thosecontacts, address books, logs, and/or the like, and/or portions thereof,in a manner analogous to that discussed above with respect to nodesand/or other computers referenced by contacts, address books, logs,and/or the like, and/or portions thereof that had been received from thenode and/or other computer from which the one or more identity requestmessages originated.

Accordingly, in various embodiments, handling of the received one ormore identity request messages by the one or more servers and/or thelike could traverse social connections among nodes and/or othercomputers, characterized, for instance, by node and/or other computerreferences in received contacts, address books, logs, and/or the like,in a manner perhaps analogous to that discussed above with respect toidentity request messages wherein, for example, identity requestmessages are propagated among nodes and/or other computers in accordancewith social connections.

In various embodiments of the present invention, having received suchone or more identity request messages the one or more centralizedservers and/or the like could, in the case where one or more identifiersand/or corresponding hashes were received therewith, act to, perhaps ina manner analogous to that discussed above, make a message available forlater retrieval by one or more appropriate nodes and/or other computers(e.g., one or more nodes and/or other computers corresponding to the oneor more identifiers and/or corresponding hashes), the message seekingpermission to provide identity information and/or one or morecorresponding profiles for the appropriate one or more individuals,businesses, and/or the like. Such functionality could, for example, beimplemented in a manner analogous to that discussed above (e.g., pollingfunctionality could be employed).

In the case where appropriate permission was granted, the one or moreservers and/or the like could act, perhaps in a manner analogous to thatdiscussed above (e.g., via polling functionality), to provide to thenode and/or other computer that dispatched the one or more identityrequest messages appropriate identity information and/or one or morecorresponding profiles for the appropriate one or more individuals,businesses, and/or the like. It is noted that, in various embodiments, anode and/or other computer so granting permission could act to encryptappropriate profiles and/or identity information (e.g., a telephonenumber) and forward the encrypted profiles and/or identity information othe one or more servers and/or the like.

Encryption might, in various embodiments, be done using a public keycorresponding to the node and/or other computer from which the one ormore identity request messages originated. The encrypted profiles and/oridentity information could then be made available by the one or moreservers and/or the like (e.g., via polling functionality) to the nodeand/or other computer from which the one or more identity requestmessages originated.

It is further noted that, in various embodiments, in providing pollingfunctionality the one or more servers and/or the like may identifymessages and/or the like available for a node and/or other computer byan encrypted, hashed, and/or the like identifier corresponding to thenode and/or other computer, and a node and/or other computer polling theone or more servers and/or the like might, in various embodiments, checkfor messages associated with its, perhaps encrypted, hashed, and/or thelike, identifier.

It is noted that, in various embodiments, various functionalityregarding evaluation, rankings, and/or the like of the sort discussedabove could be provided in centralized operation, with suchfunctionality, in various embodiments, being implemented in a manneranalogous to that discussed above.

Rankings, evaluations, and/or the like could be provided, for instance,along with a response to one or more identity request messages, and/orcould be provided otherwise (e.g., responsive to a search request and/orseparately) but perhaps in a similar manner. In various embodiments,perhaps in a manner analogous to that discussed above, option could begiven, for instance, to provide a new ranking, evaluation, and/or thelike, and/or to employ a previously provided ranking, evaluation, and/orthe like.

Accordingly, for example, rankings, evaluations, and/or the like couldbe made available to a node and/or other computer (e.g., one from whichthe one or more identity request messages originated). Suchfunctionality could, in various embodiments, be implemented in a manneranalogous to that discussed above (e.g., via polling SMS, MMS, SSH, TCP,and/or the like). In various embodiments, statistical representations(e.g., averages) that took into account stored previous evaluations,rankings, and/or the like could be made available to a node and/or othercomputer (e.g., one from which one or more identity request messagesoriginated).

In various embodiments, the one or more servers and/or the like could,perhaps via operations of the sort discussed above, come to know ofvarious evaluations, rankings, and/or the like specified by variousindividuals with respect to various individuals, businesses, and/or thelike. The one or more servers and/or the like could, in variousembodiments, employ such received evaluations, rankings, and/or the likein a number of ways. For example, such evaluations, rankings, and/or thelike could be employed such that search requests would have a higherprobability of yielding highly-regarded individuals, businesses, and/orthe like than less highly-regarded individuals, businesses, and/or thelike. Such functionality could, for instance, be implemented in a manneranalogous to that discussed above.

It is noted that, in various embodiments, in the case where a depthindicator is included one or more received search messages and/oridentity request messages in centralized operation, the one or moreservers and/or the like might act in a manner analogous to thatdiscussed above with regard to the depth indicator. It is further notedthat, in various embodiments, a combination of centralized operation andnon-centralized operation may be employed.

It is additionally noted that, in various embodiments, the one or moreservers and/or the like might act to hold, have access to, and/or thelike search, identity request, ranking messages, and/or the like, butperhaps not various of the other data and/or the like discussed above.Accordingly, for instance, nodes and/or other computers mightperiodically poll the one or more servers and/or the like for messages.Hashed phone numbers and/or the like might, in various embodiments, beemployed. In the case where there were one or more messages for a nodeand/or other computer, its user, and/or the like (e.g., searchmessages), the node and/or other computer could, for instance, receiveindication of such. The node and/or other computer might, for example,perhaps after informing its user of the one or more messages, act toeffectuate reply, forwarding of one or more of the messages, and/or thelike. The originator of the search could, for example, receive the replythe next time it polled the one or more servers and/or the like. Thenodes and/or other computers to which forwarding was directed might, forexample, receive the forwarded one or more messages the next time theypolled the one or more servers and/or the like, and could, perhaps,respond.

Further Functionality

According to various embodiments of the present invention, variousfunctionality could be implemented so as to enhance privacy, security,and/or the like. For instance, in various embodiments wildcard queriesmay be forbidden, participating address books, contacts, logs, and/orthe like might need to be of at least a certain size (e.g., 10 entries),and/or the number of nodes and/or other computers whose contacts,address books, logs, profiles, and/or the like were involved in anoperation might need to be of at least a certain value (e.g., two). Suchvalues might, in various embodiments, be set by a system administrator,service provider, and/or the like. Moreover, as discussed above, variousdata may, in various embodiments, be in encrypted form, hashed, form,and/or the like.

It is further noted that, in various embodiments, intermediate nodesand/or other computers could be employed in order to, for instance,enhance privacy, security, and/or the like. Accordingly, for example, anode and/or other computer making a dispatch (e.g., of one or moresearch messages, one or more identity request messages, of one or moreprofiles and/or the like, and/or portions thereof), might act to makethe dispatch to a node and/or other computer that would, in turn, passthe dispatch to the intended target.

Such an intermediate node and/or other computer might, for example, beone selected at random from contacts, address books, logs, and/or thelike held by the node and/or other computer making the dispatch. Invarious embodiments, a user could be able to specify (e.g., via a GUIand/or other interface) that intermediate nodes and/or other computersbe employed with respect to one or more particular dispatches, one ormore types of dispatches, all dispatches, and/or the like that originateat his node and/or other computer.

Via such operation, for example, the identity of the node and/or othercomputer performing the dispatch could be hidden from the intendedtarget of the dispatch. It is noted that, in various embodiments, suchnodes and/or other computers so employed to pass a received dispatch toan intended target might not be consulted in operations regarding searchmessages, identity request messages, and/or the like. It is furthernoted that, in various embodiments, a chain of multiple intermediatenodes and/or other computers might be employed.

It is further noted that, in various embodiments, encryption keys (e.g.,public and private keys) might be employed. For example, it might berequired that a node and/or other computer, before communicating withthe one or more servers and/or the like as discussed above (e.g., withrespect to a search), would need to request certification from acertification authority and/or the like. Such a request might, forexample, be sent via SMS, MMS, and/or the like. After performingappropriate operations the certification authority and/or the likecould, in various embodiments, send a private key to the node and/orother computer and a corresponding public key to the node and/or othercomputer and/or to the one or more servers and/or the like. Such keyscould, for instance, be employed in an SSH connection of the sortdiscussed above between the node and/or other computer and the one ormore servers and/or the like.

It is noted that, in various embodiments, in the case where anindividual, business, and/or the like is ranked, evaluated, and/or thelike, is identified as satisfying one or more search messages, and/orthe like, the individual, business, and/or the like might receivenotification of such. Such notification could, for instance, be providedin a manner analogous to that discussed above (e.g., via dispatch of amessage to a corresponding node and/or other computer, polling, and/orthe like). It is noted that, in various embodiments, one or moreintermediate nodes and/or other computers could be employed in suchnotification. It is further noted that, in various embodiments, one ormore corresponding values could be imparted via such notification.

In various embodiments, one or more nodes and/or other computerscorresponding an individual, business, and/or the like might act,perhaps in a manner analogous to that discussed above, to make availableto, for instance, a node and/or other computer that dispatched one ormore search messages and/or identity request messages, a statisticalrepresentation (e.g., an average) of ranking, evaluation, and/or thelike for the individual, business, and/or the like, the statisticalrepresentation perhaps corresponding to a particular period of time.

It is noted that, in various embodiments, functionality described hereincould be combined with the results of search engines (e.g., Internetsearch engines), employed to improve, refine, and/or the like theresults of search engines, and/or the like. Such functionality could beimplemented in a number of ways. For instance, results returned from asearch engine might be refined via the dispatch of one or morecorresponding search messages.

It is further noted that, in various embodiments, a user's identitymight only be revealed to others (e.g., with respect to a providedsearch result, profile, ranking, evaluation, and/or the like) in thecase where the user (e.g., via a GUI and/or other interface) explicitlygave permission that his identity be revealed.

As discussed above, in various embodiments various dispatches could bewith respect to some or all of nodes and/or other computers referencedin contacts, an address book, a log, and/or the like. Such functionalitycould be implemented in a number of ways. For example, in variousembodiments, a user could be queried (e.g., via a GUI and/or otherinterface) as for specification as to what node and/or other computerreferences should be employed. (e.g., the user could be able to specifythat certain particular contacts entries, address book entries, logentries, and/or the like be employed).

As another example, a user could, in various embodiments, be able tospecify criteria as to what node and/or other computer references shouldbe employed (e.g., a user might specify that only nodes and/or othercomputers whose users are less than 30 years old receive dispatch). Suchinformation regarding node and/or other computer users (e.g., ages)might be known, for example, via data in contacts, address books, logs,and/or the like, via received profiles, and/or the like.

It is noted that, according to various embodiments of the presentinvention, a user may be able to provide various settings regardingvarious of the operations discussed herein. Such settings might, forinstance, be settable by a GUI and/or other interface provided by theuser's node and/or other computer. It is further noted that, in variousembodiments, a user could, perhaps via a GUI and/or other interface, beable to provide defaults, specifications, and/or the like regardingvarious operations described herein.

Accordingly, for example, a user might be able to provide defaults,specification, and/or the like regarding profiles (e.g., specificationas to whether a profile should be kept private, should be made availableto only nodes and/or other computers, servers, and/or the likereferenced by contacts, an address book, a log, and/or the likecorresponding to the user, should be made available to all, that theuser should be queried (e.g., via a GUI and/or other interface) beforeany profile dispatch, and/or the like).

It is noted that, in various embodiments, forwarding of messagesaccording to contacts, address books, logs, and/or the like might onlybe with respect to entities marked “public” and/or the like. It isfurther noted that, in various embodiments, Bluetooth, UWB, wirelessFirewire, IrDA, WiFi, and/or the like might be used as an extension inthe case where, for instance, operations via GPRS, UMTS, and/or the likewere unsuccessful. It is further noted that, in various embodiments,Bluetooth, UWB, wireless Firewire, IrDA, WiFi, and/or the like might beemployed such that forwarding was to proximal nodes and/or othercomputers (e.g., nodes and/or other computers in proximity forcommunication) as an alternative to and/or in addition to forwarding toone or more nodes and/or other computers referenced in contacts, addressbooks, logs, and/or the like.

It is additionally noted that, in various embodiments, searching and/orother operations discussed herein could be performed with respect toother information than that which is described herein.

In various embodiments, a profile might be populated, created, and/orthe like using data retrieved from public databases, data from a nodeand/or other computer's address books, contacts, logs, and/or the like,data from received electronic business cards, and/or the like. Invarious embodiments, such data could be filtered, sorted, and/or thelike via social network.

Hardware and Software

Various operations and/or the like described herein may be executed byand/or with the help of computers. Further, for example, devicesdescribed herein may be and/or may incorporate computers. The phrases“computer”, “general purpose computer”, and the like, as used herein,refer but are not limited to a smart card, a media device, a personalcomputer, an engineering workstation, a PC, a Macintosh, a PDA, aportable computer, a computerized watch, a wired or wireless terminal,phone, node, and/or the like, a server, a network access point, anetwork multicast point, a set-top box, a personal video recorder (PVR,a game console, or the like, perhaps running an operating system such asOS X, Linux, Darwin, Windows CE, Windows XP, Windows Server 2003, PalmOS, Symbian OS, or the like, perhaps employing the Series 40 Platform,Series 60 Platform, and/or Series 90 Platform, and perhaps havingsupport for Java and/or .Net.

The phrases “general purpose computer”, “computer”, and the like alsorefer, but are not limited to, one or more processors operativelyconnected to one or more memory or storage units, wherein the memory orstorage may contain data, algorithms, and/or program code, and theprocessor or processors may execute the program code and/or manipulatethe program code, data, and/or algorithms. Accordingly, exemplarycomputer 4000 as shown in FIG. 4 includes system bus 4050 whichoperatively connects two processors 4051 and 4052, random access memory4053, read-only memory 4055, input output (I/O) interfaces 4057 and4058, storage interface 4059, and display interface 4061. Storageinterface 4059 in turn connects to mass storage 4063. Each of I/Ointerfaces 4057 and 4058 may, for example, be an Ethernet, IEEE 1394,IEEE 1394b, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11i, IEEE802.11e, IEEE 802.11n, IEEE 802.15a, IEEE 802.16a, IEEE 802.16d, IEEE802.16e, IEEE 802.16x, IEEE 802.20, IEEE 802.15.3, ZigBee, Bluetooth,Wireless Universal Serial Bus (WUSB), wireless Firewire, terrestrialdigital video broadcast (DVB-T), satellite digital video broadcast(DVB-S), Digital Audio Broadcast (DAB), General Packet Radio Service(GPRS), Universal Mobile Telecommunications Service (UMTS), GlobalSystem for Mobile Communications (GSM), DVB-H (Digital VideoBroadcasting: Handhelds), IrDA (Infrared Data Association), and/or otherinterface.

Mass storage 4063 may be a hard drive, optical drive, or the like.Processors 4051 and 4052 may each be a commonly known processor such asan IBM or Motorola PowerPC, an AMD Athlon, an AMD Opteron, an Intel ARM,an Intel XScale, a Transmeta Crusoe, a Transmeta Efficeon, an IntelXenon, an Intel Itanium, or an Intel Pentium. Computer 4000 as shown inthis example also includes a touch screen 4001 and a keyboard 4002. Invarious embodiments, a mouse, keypad, and/or interface might alternatelyor additionally be employed. Computer 4000 may additionally include orbe attached to card readers, DVD drives, floppy disk drives, harddrives, memory cards, ROM, and/or the like whereby media containingprogram code (e.g., for performing various operations and/or the likedescribed herein) may be inserted for the purpose of loading the codeonto the computer.

In accordance with various embodiments of the present invention, acomputer may run one or more software modules designed to perform one ormore of the above-described operations. Such modules might, for example,be programmed using languages such as Java, Objective C, C, C#, C++,Perl, and/or Xen according to methods known in the art. Correspondingprogram code might be placed on media such as, for example, DVD, CD-ROM,and/or floppy disk. It is noted that any described division ofoperations among particular software modules is for purposes ofillustration, and that alternate divisions of operation may be employed.Accordingly, any operations discussed as being performed by one softwaremodule might instead be performed by a plurality of software modules.Similarly, any operations discussed as being performed by a plurality ofmodules might instead be performed by a single module. It is noted thatoperations disclosed as being performed by a particular computer mightinstead be performed by a plurality of computers. It is further notedthat, in various embodiments, peer-to-peer and/or grid computingtechniques may be employed.

Shown in FIG. 5 is a block diagram of a terminal, an exemplary computeremployable in various embodiments of the present invention. In thefollowing, corresponding reference signs are applied to correspondingparts. Exemplary terminal 5000 of FIG. 5 comprises a processing unit CPU503, a multi-carrier signal terminal part 505, and a user interface(501, 502). The multi-carrier signal terminal part 505 and the userinterface (501, 502) are coupled with the processing unit CPU 503. Oneor more direct memory access (DMA) channels may exist betweenmulti-carrier signal terminal part 505 and memory 504. The userinterface (501, 502) comprises a display and a keyboard to enable a userto use the terminal 5000. In addition, the user interface (501, 502)comprises a microphone and a speaker for receiving and producing audiosignals. The user interface (501, 502) may also comprise voicerecognition (not shown).

The processing unit CPU 503 comprises a microprocessor (not shown),memory 504 and possibly software. The software can be stored in thememory 504. The microprocessor controls, on the basis of the software,the operation of the terminal 5000, such as receiving of a data stream,tolerance of the impulse burst noise in data reception, displayingoutput in the user interface and the reading of inputs received from theuser interface. The hardware contains circuitry for detecting signal,circuitry for demodulation, circuitry for detecting impulse, circuitryfor blanking those samples of the symbol where significant amount ofimpulse noise is present, circuitry for calculating estimates, andcircuitry for performing the corrections of the corrupted data.

Still referring to FIG. 5, alternatively, middleware or softwareimplementation can be applied. The terminal 5000 can, for instance, be ahand-held device which a user can comfortably carry. The terminal 5000can, for example, be a cellular mobile phone which comprises themulti-carrier signal terminal part 505 for receiving the multicasttransmission stream. Therefore, the terminal 5000 may possibly interactwith the service providers.

RAMIFICATIONS AND SCOPE

Although the description above contains many specifics, these are merelyprovided to illustrate the invention and should not be construed aslimitations of the invention's scope. Thus it will be apparent to thoseskilled in the art that various modifications and variations can be madein the system and processes of the present invention without departingfrom the spirit or scope of the invention.

What is claimed is:
 1. A method, comprising: receiving a search query,wherein the search query specifies search criteria; searching for aprofile matching the search criteria among one or more held profilescorresponding to entities; consulting a depth indicator associated withthe search query; and forwarding the search query to one or more nodeswithin a social network of a user.